Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1222

reference
667-tree-1
name
1222
tree-preservation-order

undefined

667-tpo-1
uprn
address-text
point
POINT (-1.014718 50.882171)
geometry
MULTIPOLYGON (((-1.014662 50.882165,-1.014664 50.882176,-1.014672 50.882186,-1.014684 50.882194,-1.014700 50.882200,-1.014718 50.882202,-1.014735 50.882200,-1.014751 50.882195,-1.014764 50.882187,-1.014772 50.882177,-1.014775 50.882166,-1.014773 50.882155,-1.014765 50.882145,-1.014752 50.882137,-1.014737 50.882132,-1.014719 50.882130,-1.014702 50.882131,-1.014686 50.882136,-1.014673 50.882144,-1.014665 50.882154,-1.014662 50.882165)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL